Description

Fixes issue where the "Longest Open Issues" chart was limiting results to only 7 issues when multiple projects were selected, causing some issues to be hidden. Also fixes issue numbering consistency when multiple projects are selected.

Fixes #4301 (Phase 2 Bugs - Priority Medium)
Related to Frontend PR: 4653

Main changes explained:

How to test:

1. Checkout branch vamsidhar-fix/issue-chart-all-issues-visible
2. Run npm run build to compile the changes
3. Start the backend server npm run start
4. Navigate to http://localhost:5173/bmdashboard/totalconstructionsummary
5. Test Scenario 1: Select only "Building 3"
   • Should show all Building 3 issues (e.g., "Paint Peeling in Conference Room", "Issue 1", "Issue 2", "Issue 3", "Issue 4")
6. Test Scenario 2: Select "Building 3" and "Building 1" together
   • Should show ALL issues from both projects (not limited to 7)
   • Should include all Building 3 issues (Issue 1, 2, 3, 4) AND all Building 1 issues
   • Verify no issues are missing compared to when selecting projects individually
7. Test Scenario 3: Select multiple projects with many issues
   • Verify all issues are displayed, sorted by duration (longest first)
   • Check backend console logs to verify the count of issues being returned

Expected behavior:

• When selecting multiple projects, ALL issues from all selected projects should be visible
• Issues should be sorted by duration (longest open first)
• No limit on the number of issues displayed
• Each issue should have a unique issueId for consistent identification